Skip to content

chore(deps): update dependency @brightdata/mcp to v2.9.5#469

Open
renovate[bot] wants to merge 2 commits intomainfrom
renovate/brightdata-mcp-2.x
Open

chore(deps): update dependency @brightdata/mcp to v2.9.5#469
renovate[bot] wants to merge 2 commits intomainfrom
renovate/brightdata-mcp-2.x

Conversation

@renovate
Copy link
Copy Markdown
Contributor

@renovate renovate Bot commented Apr 17, 2026

This PR contains the following updates:

Package Change Age Confidence
@brightdata/mcp 2.9.02.9.5 age confidence

Release Notes

brightdata/brightdata-mcp (@​brightdata/mcp)

v2.9.5

Compare Source

v2.9.4

Compare Source

v2.9.3

Compare Source

v2.9.3
  • New code tool group - your coding agent's companion
    • web_data_npm_package - look up any npm package by name and get back
      structured metadata: latest version, README, dependencies, and more
      (e.g. @brightdata/sdk, express, fastify)
    • web_data_pypi_package - look up any PyPI package by name and get back
      structured metadata: latest version, README, dependencies, and more
      (e.g. langchain-brightdata, requests, numpy)
    • Enable with GROUPS="code" - works with Claude Code, Cursor, Windsurf,
      and any MCP-powered coding agent
  • Added code group row to the tool groups table in README
  • Added coding agent configuration example in README
Why this matters

Coding agents constantly need to answer questions like "what's the latest
version of X?"
or "what does this package do?". Until now that meant
scraping registry pages or relying on stale training data. The code group
gives agents a single, reliable tool to query npm and PyPI directly —
structured data, no scraping, no blocking, always up to date.

v2.9.2

Compare Source

v2.9.1

Compare Source


Configuration

📅 Schedule: (UTC)

  • Branch creation
    • At any time (no schedule defined)
  • Automerge
    • At any time (no schedule defined)

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.


  • If you want to rebase/retry this PR, check this box

This PR was generated by Mend Renovate. View the repository job log.

@github-advanced-security
Copy link
Copy Markdown

You are seeing this message because GitHub Code Scanning has recently been set up for this repository, or this pull request contains the workflow file for the Code Scanning tool.

What Enabling Code Scanning Means:

  • The 'Security' tab will display more code scanning analysis results (e.g., for the default branch).
  • Depending on your configuration and choice of analysis tool, future pull requests will be annotated with code scanning analysis results.
  • You will be able to see the analysis results for the pull request's branch on this overview once the scans have completed and the checks have passed.

For more information about GitHub Code Scanning, check out the documentation.

@github-actions
Copy link
Copy Markdown

github-actions Bot commented Apr 17, 2026

🔒 MCP Security Scan Results

⚠️ brightdata-mcp

  • Status: Warning
  • Message: No JSON output found in scan results (insecure_ignore is enabled)

Summary: Scanned 1 MCP server(s), all passed security checks. ✅

@renovate renovate Bot force-pushed the renovate/brightdata-mcp-2.x branch from a5747b8 to f0ae7d1 Compare April 20, 2026 11:05
@renovate renovate Bot changed the title chore(deps): update dependency @brightdata/mcp to v2.9.4 chore(deps): update dependency @brightdata/mcp to v2.9.5 Apr 20, 2026
@renovate renovate Bot force-pushed the renovate/brightdata-mcp-2.x branch 2 times, most recently from 3eddbeb to 674490c Compare April 21, 2026 08:19
@rdimitrov
Copy link
Copy Markdown
Member

@renovatebot rebase

@renovate renovate Bot force-pushed the renovate/brightdata-mcp-2.x branch from 674490c to bd05bc0 Compare April 21, 2026 15:31
@renovate
Copy link
Copy Markdown
Contributor Author

renovate Bot commented Apr 21, 2026

Edited/Blocked Notification

Renovate will not automatically rebase this PR, because it does not recognize the last commit author and assumes somebody else may have edited the PR.

You can manually request rebase by checking the rebase/retry box above.

⚠️ Warning: custom changes will be lost.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants